Expand and document PSRT coordination process#1769
Conversation
Documentation build overview
Show files changed (6 files in total): 📝 4 modified | ➕ 2 added | ➖ 0 deleted
|
Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com> Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
for more information, see https://pre-commit.ci
|
The diagram lines are hard to read in dark mode, can we adjust them? Details
|
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
|
@hugovk I'm coming to the unfortunate conclusion that maybe Mermaid is more work than it's worth. I remember this language and the tooling around it being so much nicer in the past :/ Oh well. I think I'm going to instead use an ASCII diagram unless there's a better method for diagramming you know of? |
|
Here is how the graph would look as an ASCII diagram, light and dark modes included: 
|
for more information, see https://pre-commit.ci
willingc
left a comment
willingc
left a comment
There was a problem hiding this comment.
Thanks @sethmlarson. Good stuff. 🌻 I'm going to merge as is.
Any additional suggestions or needed changes can be covered in a future PR.
|
Should we hold a vote for the process change (automatically assigning people)? |
|
Thank you for the review and merge @willingc 🙏 @StanFromIreland Auto-assigning coordinators to idle issues and whether this process was clear and easy to follow was the feedback I was hoping for in this thread. I have not received any feedback beyond the reviews here despite multiple reminders to PSRT and admins. I can open a separate thread on this specific point: I want folks to be okay with being assigned tasks to do (and I acknowledge it feels different than picking up tasks yourself) but it is the mission of the team to coordinate vulnerability reports. |
|
FYI PSRT: a thread was opened in the Discord. |
4 participants
This PR defining the coordination process more concretely. Here are the changes:
cc @python/psrt